Skip to content

deps: Update all bundler plugin instances to latest & allow caret ranges #16641

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

mydea
Copy link
Member

@mydea mydea commented Jun 18, 2025

If a version is released with a buggy bundler plugin dependency pinned, it can lead to problems. IMHO it should be fine to allow ^ ranges there to ensure bugfixes etc. are pulled in? Or is there a good reason not to do that here? API should be stable in this regard.

Note: Astro& solidstart remain on @sentry/vite-plugin v2.x as that has more stuff exposed, did not want to get into that right now... something for v10?

@mydea mydea self-assigned this Jun 18, 2025
@mydea mydea force-pushed the fn/unpin-plugin-version branch from b587870 to d2e86c2 Compare June 18, 2025 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants